User Notifications for Interaction Information

ABSTRACT

A content management system creates and modifies user notification queues for shared content items synchronized between a content management system and multiple devices. A user notification queue includes interactions with a shared content item that may be presented to a user to indicate recent interactions with the shared content item by other sharing users. The content management system sends the user notification queue corresponding to a user to the user&#39;s device when the user accesses the content item. The client device displays a content item in a window associated with a process on the device. A client application displays an interaction indicator that presents user notification queue content to the user.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/727,566, filed Oct. 7, 2017, now U.S. patent Ser. No. ______, whichis a continuation of U.S. application Ser. No. 15/424,913, filed Feb. 6,2017, now U.S. Pat. No. 9,826,004, which is a continuation of U.S.application Ser. No. 15/171,875, filed Jun. 2, 2016, now U.S. Pat. No.9,596,276, which is a continuation of U.S. application Ser. No.14/985,552, filed on Dec. 31, 2015, now U.S. Pat. No. 9,413,708, each ofwhich is incorporated by reference.

BACKGROUND

This disclosure relates generally to sharing information among devices,and particularly to interactions between native software applicationsand shared content.

Content management systems permit devices to synchronize content itemswith the content management system and other devices. A device stores alocal copy of content items. When content items are added, deleted, andedited on a device, these modifications are sent to the contentmanagement system for storage and synchronization with other devices. Tointeract with a content item, users typically execute a nativeapplication on the device to view and modify the content item. Whenmultiple users interact with a content item, they often communicateabout the content item using other applications such as email. This typeof communication provides an incomplete picture of interactions with thecontent item and relies on users to log and track interactions with thecontent item. Users lack a convenient way to communicate about a contentitem and view interactions with the content item, which addsinconvenience and complexity to situations in which multiple users areinteracting with a content item.

SUMMARY

Described embodiments enable device users sharing content items via acontent management system to view and modify content items within nativeapplications on their client devices. In various embodiments, usernotification queues are created, modified and sent to client devices,and graphical and textual information is provided to users on theirrespective devices indicating interactions with a shared content item onone or more other devices.

A device in accordance with various embodiments stores a local copy of ashared content item, which is maintained and synchronized betweendevices by a content management system. The device includes a nativeapplication that can be used to access the content item, such as a wordprocessor, media viewer, media editor, and so forth. The nativeapplication displays the content item in a user interface element, suchas a window. The device also includes a client application, in additionto the native application, which monitors interactions with the contentitem and communicates information about those interactions to otherdevices sharing the content item either directly or via the contentmanagement system.

Interaction information includes interactions by users with the clientapplication and interactions by users with the native application.Interaction information may be determined from interaction events, suchas messages, notes, collaboration requests, and presence events.Presence events are programmatic events that occur in the nativeapplication. Presence events include opening a content item, editing acontent item, saving a content item, renaming a content item, moving acontent item, and deleting a content item. Presence events also includeinteractions with the user interface elements of the native application,such as the user interface element gaining or losing focus. A focuseduser interface element is the user interface element that receives userinputs at the device. For example, if a user interface element hasfocus, presence information may be generated indicating that a user is“viewing” the content item via that user interface element. In oneembodiment, the presence events are gathered by the client application,which is separate from the native application interacting with thecontent item. That is, in this embodiment the presence events aregathered by another application or process that is not integrated intothe native application accessing the content item or the presenceinformation.

Additional types of interaction information that may be received by theclient application include notes, messages, notification requests, andcollaboration requests related to the content item. Messages may includechat messages to other devices and messages indicating a user's intentto interact with (e.g., to edit) a content item. Interaction informationalso includes metadata modifications, such as versioning notes, orrequests for further information stored at the content management systemabout the content item, such as a request to view versioning informationor prior content item versions. The interaction information is exchangedby the devices to provide users with information regarding others'interactions with the content item.

The client application monitors events on the device to determine when auser is using a native application to interact with a content item. Inone method of monitoring events, the client application registers with aprocess controlling a user interface element or the operating system toreceive events related to the user interface element. The clientapplication may monitor all such events, or only certain user interfaceelements associated with opening a content item. When a presence eventoccurs, the client application receives the presence event from thenative application or from an operating system. The client applicationidentifies a user interface element associated with the event anddetermines presence information associated with the event. The clientapplication notifies the content management system that synchronizedcontent items are being or have been interacted with, and sends thepresence information to the content management system. The presenceinformation (or other interaction information) may be sent directly toother devices.

The content management system receives interaction information andcreates, modifies, and sends user notification queues for content itemsto devices of sharing users. A user notification queue is a group of oneor more interactions with a shared content item that may be presented toa user to indicate recent interactions with the shared content item bysharing users. In one embodiment, each sharing user associated with acontent item has a user notification queue corresponding to that contentitem. Types of interactions added to a user notification queue mayinclude content item views, content item edits, content itemcollaborations, content item comments, and content item messages. In oneembodiment, interactions have an associated interaction priority. Aninteraction priority specifies a relative priority of an interactiontype to other interaction types. A notification queue module determinesthe interaction types and interaction priorities for candidateinteractions and interactions in user notification queues. In variousembodiments, the notification queue module selects higher priorityinteractions to add to user notification queues and lower priorityinteractions to remove from user notification queues.

When a user views a content item in a native application of a device,the content management system receives a notification and sends theappropriate user notification queue to the device. The clientapplication displays interaction information about the content item. Inone embodiment, the client application provides one or more interactionindicators in a user interface of the device. An interaction indicatordisplays interaction information to users. This permits users to view,in essentially real or near real-time, the activity of other users withrespect to a content item. In addition, presenting interfaces tocommunicate with the content management system alongside the nativeapplication user interface permits users to conveniently exchange chatinformation and retrieve data about a content item while the contentitem is being displayed.

The client application or the content management system may determinewhether a user has been provided with a notification about interactioninformation or has viewed interaction information displayed in the userinterface, and may send this information to the content managementsystem and other devices associated with the user so that theinteraction information that has been viewed by a user is tracked acrossmultiple devices. Using this information, the client application canavoid duplicating notifications so that users are not notified about thesame interactions on several devices.

In one embodiment, the interaction indicator includes a badge elementindicating unviewed interaction information, including notificationqueue content. The user may select the interaction indicator to viewmore interaction information. The client application may further displayan interaction element for a user to view and enter interactioninformation. Interaction information may be displayed in a notificationchannel style along with metadata and other information, such as eventtimes and user information. The interaction element may further includechat functionality, including a text input element or other chatinterface. This permits users to chat directly about a content item,even if the native application provides no chat functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an embodiment of an environment for content itemsynchronization including communication of interaction information anduser collaboration

FIG. 2 shows various modules and components of a device in accordancewith one embodiment.

FIGS. 3A and 3B show a user interface element focus change on a desktopdisplay of a device.

FIG. 4 shows components of a content management system, according to oneembodiment.

FIG. 5 shows an example process for determining presence informationassociated with a content item according to one embodiment.

FIGS. 6A-6D show example user interfaces displaying interactioninformation.

FIG. 7 shows an example process for updating notification queues forsharing users according to one embodiment.

FIG. 8 shows an example process for sending a notification queue to adevice accessing a content item according to one embodiment.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION

FIG. 1 shows an embodiment of an environment for content itemsynchronization including communication of interaction information. FIG.1 includes devices 100A, 100B, 100C (referred to generally as device100), content management system 110, and network 120. Three devices areshown only for purpose of illustration; in practice any number ofdevices may be present in the environment. Similarly, other modules orcomponents described and illustrated throughout may include single ormultiple instances as appropriate to the needs of the implementer andwithout loss of generality.

Device 100 may be any suitable computing device for locally storing andviewing content items and synchronizing the content items with contentmanagement system 110. Examples of devices include desktop and laptopcomputers, hand-held mobile devices, tablet computers, and othercomputing devices. The operation of device 100 in various embodiments isfurther described below.

Each device 100 communicates with content management system 110 throughnetwork 120. Network 120 is any suitable network and may include localnetworks, corporate networks, global networks, and any combination ofthese. In typical configurations, devices 100 communicate via a wired orwireless communication network to a local network service provider, andcommunicate with content management system 110 through the Internet. Incertain configurations, devices 100A, 100B, and 100C communicatedirectly with one another without network 120 as indicated in FIG. 1 bydashed lines. For example, devices 100 may communicate via a wired orwireless connection, such as wirelessly via a Bluetooth connection or awired connection via a Universal Serial Bus (USB).

Content management system 110 provides content sharing andsynchronization services for users of devices 100. These services allowusers to share content with users of other devices 100. In addition tocontent sharing, content management system 110 updates shared contentresponsive to changes and enables synchronized changes to content itemsacross multiple devices 100. A user may synchronize content acrossmultiple devices 100 owned by the user and associated with the user'saccount, and the user may share content that is synchronized withdevices associated with other users' accounts. Content stored by contentmanagement system 110 can include any type of data, such as digitaldata, documents, media (e.g., images, photos, videos, audio, streamingcontent), data files and databases, source and object code, recordings,and any other type of data or file, collectively referred to here as“content items.” Content items stored by content management system 110may also be used to organize other content items, such as folders,tables, collections, albums, playlists, or in other database structures(e.g., object oriented, key/value etc.). In practice, various devices100 may be synchronizing different groups of content items, based onuser associations, permissions, content sharing permissions, and soforth. The operation of content management system 110 in variousembodiments is further described below with respect to FIG. 4.

FIG. 2 shows various modules and components of device 100 in accordancewith one embodiment. Device 100 includes display 220 for providinginformation to the user, and in certain client devices 100 includes atouchscreen. Device 100 also includes network interface 225 forcommunicating with content management system 110 via network 120. Device100 also includes a user input module 260, which receives user inputsfrom various user input devices, such as a keyboard, a mouse, atrackpad, or other device. Other conventional components of a clientdevice 100 that are not material are not shown, for example one or morecomputer processors, local fixed memory (RAM and ROM), as well asoptionally removable memory (e.g., SD-card), power sources, andaudio-video outputs.

Software modules include operating system 245 and one or more nativeapplications 255. Native applications 255 vary based on the clientdevice, and may include various applications for creating, viewing,consuming, and modifying content stored on content management system110, such as word processors, spreadsheets, database management systems,code editors, image and video editors, e-book readers, audio and videoplayers, and the like. Operating system 245 on each device provides alocal file management system and executes the various software modulessuch as content management system client application 200 and nativeapplication 255. A contact directory 240 stores information about theuser's contacts, such as name, picture, telephone numbers, company,email addresses, physical address, website URLs, and the like. Furtheroperation of native applications 255, operating system 245, and contentmanagement system client application 200 are described below.

In certain embodiments, device 100 includes additional components suchas camera 230 and location module 235. Camera 230 may be used to captureimages or video for upload to the online content management system 110.Location module 235 determines the location of device 100, using forexample a global positioning satellite signal, cellular towertriangulation, or other methods. Location module 235 may be used byclient application 200 to obtain location data and add the location datato metadata about a content item, such as an image captured by camera230.

Client device 100 accesses content management system 110 in a variety ofways. Client application 200 can be a dedicated application or modulethat provides access to the services of content management system 110,providing both user access to shared files through a user interface, aswell as programmatic access for other applications. Client device 100may also access content management system 110 through web browser 250.As an alternative, client application 200 may integrate access tocontent management system 110 with the local file management systemprovided by operating system 245. When access to content managementsystem 110 is integrated in the local file management system, a fileorganization scheme maintained at content management system 110 isrepresented as a local file structure by operating system 245 inconjunction with client application 200. Client application 200 may takevarious forms, such as a stand-alone application, an applicationplug-in, or a browser extension. Client application 200 includes userinterface module 202, interaction management module 204, content accessmodule 206, local content data store 208, monitored presence data store210, and collaboration module 207.

In addition to handling other device tasks, operating system 245displays information from applications executing on device 100 to a uservia display 220, which may include one or more user interface elements.Such user interface elements may vary based on the particular device andconfiguration. User interface elements include windows on a desktopinterface as well as interface elements on a mobile device. Examples ofoperating systems that employ user interface elements such as windowsare Microsoft Windows 8 by Microsoft Corporation of Redmond, Wash., andOS X by Apple Inc. of Cupertino, Calif. In addition, operating system245 manages control of multiple native applications 255, which may beexecuting simultaneously. The user interface elements may be layered,such that one layer overlaps another layer. In some operating systemsand configurations, only a single user interface element is displayed ata given time. One user interface element is typically the active userinterface element, meaning that it is the user interface element towhich the operating system 245 routes user inputs, such as keyboardentry, cursor movement, touch sensors, touch gestures, and so forth. Asunderstood by those of skill in the art, a window or other userinterface element that is active at a particular time is often said tohave focus. Users may select another user interface element to changethe focus from one user interface element to another, and in someinstances operating system 245 may change the focus without user input.

Typically, the user interface elements, e.g., windows, associated withnative applications 255 are managed by operating system 245, whichmaintains an association between process identifiers of executing nativeapplications 255 and user interface element identifiers of the userinterface elements. For example, a particular application may beassociated with process id “2587”, which may be managing multiple userinterface elements, with user interface element identifiers 4, 8, and10. Each user interface element identifier may be separately associatedwith a particular content item opened by that native application 255,and multiple user interface element identifiers and process identifiersmay be associated with the same content item.

Operating system 245 also handles and recognizes various events. Suchevents include a request from native applications 255 to close or open acontent item, a request from native applications 255 to close a windowor other user interface element, and requests to change a user interfaceelement focus, among many others. As described below, these events maybe used by interaction management module 204 to recognize a change inpresence related to a content item.

Client application 200 identifies interactions that take place withrespect to a content item, such as when a user opens, closes or editsthe content item on the device. These interactions are identified byclient application 200 to generate interaction information describingthe interaction with the content item. Interaction information includesinteractions with client application 200 and interactions with nativeapplication 255. Interaction information determined from actionsperformed within native applications 255 is termed presence information.An application, such as client application 200 that determinesinteraction information and presence information is termed a presenceapplication. Additional types of interaction information (in addition topresence information) include notes, messages, and notification requestsrelated to the content item, which may be received by client application200. Messages may include chat messages to other devices, messagesindicating a user's intent to interact with (e.g., to edit) a contentitem, and messages indicating a user's intent to begin a collaborationsession. Notification requests may include a request to be notified whenanother user's interaction information changes. Interaction informationalso includes metadata modifications, such as versioning notes, eventtimestamps, or requests for further information stored at contentmanagement system 110 about the content item, such as a request to viewversioning information or prior content item versions. Further examplesof interaction information are described below. Client application 200may receive chat or intent information from a user. In variousembodiments, device 100 identifies a user's presence in a content item(i.e. that the user has the content item open or is editing the contentitem using the native application 255) through interaction withoperating system 245 as described further below. Interaction informationis transmitted to other devices 100 that are synchronized with respectto the content item.

Device 100 receives content items from content management system 110 andpermits users to view, modify, and interact with the content items usingvarious native applications 255 stored on the device 100. For example,device 100 may include a photo editing application that manipulatesimage content items, a word processing application that permitsmodification of text content items, or a computer-aided design (CAD)application that permits modification of drawing content items. Asdescribed further below, interaction information is determined by device100 via user interactions applications and the interaction informationis sent to other devices 100. In addition, when device 100 receivesinteraction information relating to other devices 100, the device 100displays that interaction information.

In one embodiment, an application detecting interaction informationrelating to content items is distinct from the applications viewing ormanipulating the content items. For example, the client applicationdetecting interaction information is distinct from a photo editingapplication manipulating or displaying the image content items. Invarious embodiments, the application detecting interaction informationis also responsible for synchronizing the content items with contentmanagement system 110. Since the application detecting presenceinformation may be distinct from the applications about which presenceis detected, presence may be monitored for many applications and contentitems at once and without requiring integration of the presencemonitoring into each type of content item viewer. That is, no specialpresence monitoring add-on or application modification is required, forexample, for each of a photo editing application, a word processingapplication, and a playlist editing application.

FIGS. 3A and 3B show an example of a user interface element focus changeon desktop 300 shown on display 220 of device 100. In FIG. 3A, windows310A, 310B, and 310C are displayed on desktop 300 and viewable by theuser. In this embodiment, desktop 300 is a general container or framemaintained by operating system 245 that encloses user interface elementson display 220. In FIGS. 3A and 3B, the user interface elements arewindows 310 in a desktop computing environment. In other configurations,such as a mobile device, or other display with limited area, only asingle user interface element might be displayed at a time. As shown byFIG. 3A, window 310A is the active window, shown as the front window,partially obscuring windows 310B and 310C. In FIG. 3B, focus changed towindow 310B, which is now the front window and the active window. Thefocus may change due to user interaction with window 310B, or due to aprocess requesting that its window become the active window. In certainoperating systems and configurations, a user interface element has focus(e.g., is receiving user input) without being the front user interfaceelement.

Referring again to FIG. 2, to open a content item, native application255 requests the content item from operating system 245 and receives ahandle to the content item from operating system 245 for the contentitem. In some cases, application 245 does not maintain the handle, andmay load the content item data into memory and subsequently close thecontent item handle even if native application 255 continues to use datafrom the content item or if the user enters edits to the content item.Accordingly, open content item handles are often not a reliable way todetermine whether an application is interacting with a particularcontent item. As such, in certain embodiments, further behaviorsexhibited by the native applications 255 are used to determine whetheran application is editing a content item.

Native applications 255 also perform various behaviors when a usermodifies a content item, and prior to the user saving the content item.These behaviors vary based on the application and operating system 245.For example, some native applications 255 create a temporary contentitem with a filename that differs from the open content item, forexample leading the temporary content item's filename with a tilde orother recognizable mark. In other examples, the native applications 255changes the title of a user interface element associated with thecontent item, which may or may not be directly viewable by a user. Instill further examples, native application 255 sets a flag indicatingthe content item has been modified. Native application 255 may alsoprovide information regarding content item modification in response to arequest from another application or the operating system. For examplethe Accessibility API in the OS X operating system as described aboveprovides information regarding content items associated with a userinterface element. Since an open content item handle may not reliablydetermine whether a content item is being edited by a native application255, these behaviors are used by presence management module 204 todetermine presence relating to editing or modifying a content item asdescribed further below.

Native applications 255 may typically be executed on device 100independently from one another, and may permit communication between theapplications and other applications or processes executing on device100. Native applications 255 typically provide information to processesusing application programming interfaces (APIs), which permitapplications to request information from the executing process. Forexample, native applications 255 may present an API permitting a requestfor user interface elements controlled by the application, or toindicate the title of a user interface element, or to request a path ina file system associated with a content item opened by the nativeapplication 255. Similarly, operating system 245 may provide similarAPIs to requesting processes, such as requesting information about aprocess that controls a particular user interface element.

Client application 200 manages access to content management system 110.Client application 200 includes user interface module 202 that generatesan interface to the content accessed by client application 200, asvariously illustrated herein, and is one means for performing thisfunction. The generated interface is provided to the user by display220. Client application 200 may store content accessed from a contentstorage at content management system 110 in local content data store208. While represented here as within client application 200, localcontent data store 208 may be stored with other data for client device100 in non-volatile storage. When local content data store 208 is storedthis way, the content is available to the user and other applications ormodules, such as native application 255, when client application 200 isnot in communication with content management system 110. Content accessmodule 206 manages updates to local content data store 208 and usessynchronization logic to communicate with content management system 110to synchronize content modified by client device 100 with contentmaintained on content management system 110. One example of suchsynchronization is provided in U.S. Pat. No. 9,053,165, filed Sep. 27,2013 and is hereby incorporated by reference in its entirety. Clientapplication 200 may take various forms, such as a stand-aloneapplication, an application plug-in, or a browser extension.

Content management system 110 may provide additional data forsynchronizing content items, such as information designating that acontent item has been deleted, or that the device 100 may be viewing orediting an outdated version of a content item.

Interaction management module 204 obtains and manages interactioninformation relating to a user's synchronized content items. Asdescribed above, the interaction management module 204 is typically adistinct module from the native applications 255 being monitored byinteraction management module 204 for presence information and executesas a separate process. Interaction management module 204 detectsinteraction events occurring on device 100 for synchronized contentitems. Interaction management module 204 may detect interaction eventsby monitoring presence events, or by monitoring received user inputssuch as comments and messages. Interaction events indicate that a userhas interacted with a content item. Interactions include viewing thecontent item, editing the content item, commenting on the comment item,sending a message related to the content item, and collaborating in thecontent item. Interaction management module 204 sends notificationsabout interaction events and other interaction information to contentmanagement system 110. Interaction management module 204 also receivesinteraction information, including user notification queues, relating toother users' interactions with content items from content managementsystem 110 for display to the user. In one embodiment the interactionmanagement module 204 displays interaction information from usernotification queues by attaching an interaction indicator to a userinterface element associated with a synchronized content item. Invarious embodiments, the interaction indicator and associated userinterface elements display real-time interaction information, such aspresence information, and interaction information relating to pastactivities. This allows users to view the content item and associatedinteraction information simultaneously, which provides a more holisticview of a content item, users associated with the content item, andchanges made to the content item.

In one embodiment, the interaction management module 204 providesreceived notification queue content and other interaction informationfor display in chronological order so that users may view a sequence ofinteractions with the content item. Displayed interaction informationmay include metadata such as timestamps, user identifiers, user photos,and other data. In another embodiment, the interaction module displaysinteraction information as it is received in a notification channelstyle. When a new piece of interaction information is received via theuser interface, from another device 100, or from the content managementsystem 110, it is added to the channel, and users may be notified by theinteraction indicator, another user interface element, or by some othermethod. Displaying interaction information, including notifications, isdiscussed in more detail below with respect to FIGS. 6A-6D.

In one embodiment, the interaction management module 204 detects when auser has been provided with a notification about interaction informationor has viewed interaction information displayed in the user interface.The interaction management module 204 may send this information to thecontent management system 110 and/or other devices 100 associated withthe user and the content management system 110 so that the interactioninformation that has been viewed by a user is tracked across multipledevices 100. Using this information, the interaction management module204 or the content management system 110 can determine whether a userhas viewed interaction information, or been provided with a notificationabout the interaction information and avoid duplicating notifications sothat users are not notified about the same interactions on severaldevices.

To determine many types of interaction information, interactionmanagement module 204 receives interaction information through userinterface elements, as further described below. To determine presenceinformation related to a synchronized content item, interactionmanagement module 204 monitors user interface elements associated withnative applications 255. Interaction management module 204 can monitorall user interface elements, or alternatively monitor just certain userinterface elements after the user interface element is associated with acontent item. Monitored presence data store 210 includes informationmaintained by interaction management module 204 to indicate thatparticular user interface elements are monitored to determine actionsrelating to a synchronized content item.

While shown here as a part of client application 200, in variousimplementations content access module 206 and interaction managementmodule 204 are separated into distinct modules for performing theirrespective functions. Similarly, various modules and data stores aredescribed separately throughout this disclosure for convenience and invarious implementations may be combined or further separated intoseparate components as desired.

FIG. 4 shows components of content management system 110 of FIG. 1,according to one embodiment. When using content management system 110,to facilitate the various content management services a user can createan account with content management system 110. In one embodiment, theuser's account information is maintained in user account database 418.User account database 418 can store profile information for registeredusers. In some cases, the only personal information in the user profileis a username and/or email address. However, content management system110 can also be configured to accept additional user information, suchas password recovery information, demographics information, paymentinformation, and other details of interest to the implementer. Each useris associated with an identifier, such as a userID or a user name.

User account database 418 can also include account managementinformation, such as account type, e.g., free or paid; usage informationfor each user, e.g., file edit history; maximum storage spaceauthorized; storage space used; content storage locations; securitysettings; personal configuration settings; content sharing data; etc.Account management module 404 can be configured to update and/or obtainuser account details in user account database 418. Account managementmodule 404 can be configured to interact with any number of othermodules in content management system 110.

An account can be associated with multiple devices 100, and contentitems can be stored in association with an account. The stored contentcan also include folders of various types with different behaviors, orother content item grouping methods. For example, an account can includea public folder that is accessible to any user. The public folder can beassigned a web-accessible address. A link to the web-accessible addresscan be used to access the contents of the public folder. In anotherexample, an account can include a photo folder that is intended forphoto content items and that provides specific attributes and actionstailored for photos; an audio folder that provides the ability to playback audio file content items and perform other audio related actions;or other special purpose folders. An account can also include sharedfolders or group folders that are linked with and available to multipleuser accounts. The permissions for multiple users may be different for ashared folder. In one embodiment, the account is a namespace that may beassociated with several users, each of whom may be associated withpermissions to interact with the namespace.

In one embodiment, the content is stored in content storage 420. Contentstorage 420 can be a storage device, multiple storage devices, or aserver. Alternatively, content storage 420 can be a cloud storageprovider or network storage accessible via one or more communicationsnetworks. In one configuration, content management system 110 stores thecontent items in the same organizational structure as they appear on thedevice. However, content management system 110 can store the contentitems in its own order, arrangement, or hierarchy.

Content storage 420 can also store metadata describing content items,content item types, and the relationship of content items to variousaccounts, folders, or groups. The metadata for a content item can bestored as part of the content item or can be stored separately. In oneconfiguration, each content item stored in content storage 420 can beassigned a system-wide unique identifier.

Content storage 420 can decrease the amount of storage space required byidentifying duplicate content items or duplicate segments of contentitems. In one embodiment, for example, a content item may be sharedamong different users by including identifiers of the users withinownership metadata of the content item (e.g., an ownership list), whilestoring only a single copy of the content item and using pointers orother mechanisms to link duplicates with the single copy. Similarly,content storage 420 stores content items using a version controlmechanism that tracks changes to content items, different versions ofcontent items (such as a diverging version tree), and a change history.The change history includes a set of changes that, when applied to theoriginal content item version, produces the changed content itemversion.

In one embodiment, content management system 110 automaticallysynchronizes content items from one or more devices usingsynchronization module 412. The synchronization is platform-agnostic.That is, the content items are synchronized across multiple devices 100of varying type, capabilities, operating systems, etc. For example,client application 200 synchronizes, via synchronization module 412 atcontent management system 110, content in the file system of device 100with the content items in an associated user account on system 110.Client application 200 synchronizes any changes to content items in adesignated folder and its sub-folders with the synchronization module412. Such changes include new, deleted, modified, copied, or moved filesor folders. Synchronization module 412 also provides any changes tocontent associated with device 100 to client application 200. Thissynchronizes the local content at device 100 with the content items atcontent management system 110.

Conflict management module 414 determines whether there are anydiscrepancies between versions of a content item located at differentdevices 100. For example, when a content item is modified at one deviceand a second device, differing versions of the content item may exist ateach device. Synchronization module 412 determines such versioningconflicts, for example by identifying the modification time of thecontent item modifications. Conflict management module 414 resolves theconflict between versions by any suitable means, such as by merging theversions, or by notifying the device of the later-submitted version.

A user can also view or manipulate content via a web interface generatedby user interface module 402. For example, the user can navigate in webbrowser 250 to a web address provided by content management system 110.Changes or updates to content in content storage 420 made through theweb interface, such as uploading a new version of a file, aresynchronized back to other devices 100 associated with the user'saccount. Multiple devices 100 may be associated with a single accountand files in the account are synchronized between each of the multipledevices 100.

Content management system 110 includes communications interface 400 forinterfacing with various devices 100, and with other content and/orservice providers via an Application Programming Interface (API), whichis one means for performing this function. Certain software applicationsaccess content storage 420 via an API on behalf of a user. For example,a software package, such as an app on a smartphone or tablet computingdevice, can programmatically make calls directly to content managementsystem 110, when a user provides credentials, to read, write, create,delete, share, or otherwise manipulate content. Similarly, the API canallow users to access all or part of content storage 420 through a website.

Content management system 110 can also include authenticator module 406,which verifies user credentials, security tokens, API calls, specificdevices, etc., to determine whether access to requested content items isauthorized, and is one means for performing this function. Authenticatormodule 406 can generate one-time use authentication tokens for a useraccount. Authenticator module 406 assigns an expiration period or dateto each authentication token. In addition to sending the authenticationtokens to requesting devices, authenticator module 406 can storegenerated authentication tokens in authentication token database 422.Upon receiving a request to validate an authentication token,authenticator module 406 checks authentication token database 422 for amatching authentication token assigned to the user. Once theauthenticator module 406 identifies a matching authentication token,authenticator module 406 determines if the matching authentication tokenis still valid. For example, authenticator module 406 verifies that theauthentication token has not expired or was not marked as used orinvalid. After validating an authentication token, authenticator module406 may invalidate the matching authentication token, such as asingle-use token. For example, authenticator module 406 can mark thematching authentication token as used or invalid, or delete the matchingauthentication token from authentication token database 422.

Content management system 110 includes a sharing module 410 for sharingcontent publicly or privately. Sharing content publicly can includemaking the content item accessible from any computing device in networkcommunication with content management system 110. Sharing contentprivately can include linking a content item in content storage 420 withtwo or more user accounts so that each user account has access to thecontent item. The content can also be shared across varying types ofuser accounts.

In some embodiments, content management system 110 includes a contentmanagement module 408 for maintaining a content directory thatidentifies the location of each content item in content storage 420, andallows client applications to request access to content items in thestorage 420, and which is one means for performing this function. Acontent entry in the content directory can also include a contentpointer that identifies the location of the content item in contentstorage 420. For example, the content entry can include a contentpointer designating the storage address of the content item in memory.In some embodiments, the content entry includes multiple contentpointers that point to multiple locations, each of which contains aportion of the content item.

In addition to a content path and content pointer, a content entry insome configurations also includes a user account identifier thatidentifies the user account that has access to the content item. In someembodiments, multiple user account identifiers can be associated with asingle content entry indicating that the content item has shared accessby the multiple user accounts.

To share a content item privately, sharing module 410 adds a useraccount identifier to the content entry associated with the contentitem, thus granting the added user account access to the content item.Sharing module 410 can also be configured to remove user accountidentifiers from a content entry to restrict a user account's access tothe content item.

To share content publicly, sharing module 410 generates a custom networkaddress, such as a URL, which allows any web browser to access thecontent in content management system 110 without any authentication. Thesharing module 410 includes content identification data in the generatedURL, which can later be used by content management system 110 toproperly identify and return the requested content item. For example,sharing module 410 can be configured to include the user accountidentifier and the content path in the generated URL. The contentidentification data included in the URL can be transmitted to contentmanagement system 110 by a device to access the content item. Inaddition to generating the URL, sharing module 410 can also beconfigured to record that a URL to the content item has been created. Insome embodiments, the content entry associated with a content item caninclude a URL flag indicating whether a URL to the content item has beencreated.

Interaction synchronization module 416 receives presence informationfrom a device, stores it as part of a presence record in interactiondata store 424 and determines a user presence with respect to a contentitem. Each user may be associated with a user presence describingpresence records associated with that user with respect to a contentitem, which may be without reference to any particular user device,process, or user interface element. While presence information maydescribe presence with respect to a particular user interface element orprocess, this presence associated with a user is termed a user presence.Example user presence includes collaborating, editing, viewing, open,and not present. In this example, a “collaborating” user presenceindicates the content item is associated with a user interface elementthat is presented for viewing and modification on two or more devices,an “editing” user presence indicates the content item is associated witha user interface element that has modified the content item, a “viewing”user presence indicates the content item is associated with an activeuser interface element on a device 100, while an “open” user presenceindicates a user interface element is associated with the content itemand has opened the content item, but has not yet closed the contentitem. Various embodiments may use more or fewer user presences. Forexample, one embodiment includes only “editing” “viewing” and “notpresent,” in which case user interface elements that have opened thecontent item but are not the active user interface element may betreated as viewing or not presence, according to the configuration ofthe system. Obtaining and tracking presence information is also furtherdescribed in U.S. patent application Ser. No. 14/635,192, incorporatedby reference herein.

Interaction synchronization module 416 manages synchronization ofinteraction information across devices 100. Devices 100 provideinteraction information to interaction synchronization module 416.Interaction synchronization module 416 stores interaction information ininteraction data store 424. Interaction synchronization module 416 sendsinteraction information about synchronized content items to synchronizeddevices 100 for display to users. Interaction synchronization module 416may further send instructions to notify users of new or unviewedinteraction information. In one embodiment, devices 100 send viewinginformation to interaction synchronization module 416 indicating whetherand when users have viewed interaction information. Viewing informationis stored in interaction data store 424. In another embodiment, viewinginformation indicates whether and when users have interacted withinteraction information. Interaction synchronization module 416 may usethis information to avoid duplicate notifications on multiple devices100 associated with the same user. For example, if a user is notified ofnew interaction information on a first device 100 and views theinteraction information, this event will be stored such that the userwill not be notified about the same interaction information on a seconddevice 100.

In one embodiment, content management system 110 includes collaborationmodule 426. Collaboration module 426 can be configured to facilitatecollaboration between devices 100. For instance, collaboration module426 may initiate a device handshake by sharing a device's address withanother device so that collaboration may occur. Further, collaborationmodule 426 may be configured to perform any of the tasks that areperformed by collaboration module 207 of a device 100 or by any othermodule of client application 200.

Notification queue module 428 creates and manages user notificationqueues 430 for shared content items. User notification queues 430 arestored at content management system 110 and sent to devices 100. A usernotification queue 430 is a group of one or more interactions with ashared content item that may be presented to a user to indicate recentinteractions with the shared content item by sharing users. In oneembodiment, each sharing user associated with a content item has a usernotification queue 430 corresponding to that content item. Differentusers' user notification queues for a particular content item maydiffer.

In one embodiment, notification queue module 428 receives a notificationof an interaction event, and determines interactions that are candidatesto be added to user notification queues 430. The notification queuemodule 428 modifies user notification queues 430 corresponding to ashared content item. Modifying user notification queues 430 may includeadding candidate interactions to the notification queue and removinginteractions already present in the notification queue. When aninteraction event corresponding to a shared content item is received bythe content management system 110, the notification queue module 420determines whether to add interactions to and/or remove interactionsfrom the sharing users' user notification queues 430. Types ofinteractions added to a user notification queue 430 may include contentitem views, content item edits, content item collaborations, contentitem comments, and content item messages.

In one embodiment, interactions have an associated interaction priority.An interaction priority specifies a relative priority of an interactiontype to other interaction types. For example, a content item edit mayhave a higher priority than a content item view. Interaction prioritiesmay be specified by an implementer of the content management system 110or by a user of the content management system 110. The notificationqueue module 428 determines the interaction types and interactionpriorities for candidate interactions and interactions in usernotification queues 430. In various embodiments, the notification queuemodule 428 selects higher priority interactions to add to usernotification queues 430 and lower priority interactions to remove fromuser notification queues 430. For example, the notification queue module428 may compare the priority of a candidate interaction by a user A tothe priority of interactions by user A already present in a notificationqueue 430. If the candidate interaction is a lower priority interactionthan an interaction in the user notification queue 430, the candidateinteraction is not added to the queue. If the candidate interaction is ahigher priority interaction than an interaction in the user notificationqueue 430, the candidate interaction is added to the queue, and theinteraction already in the queue may be removed from the queue. Thisallows users to be presented other users' higher priority interactionswith a content item, which provides important information for the userswithout also providing less important information that may confuse theuser or waste space in a user interface element.

Notification queue module 428 may send user notification queues 430 todevices 100. In one embodiment, notification queue module 428 sends auser notification queue 430 responsive to receiving a notification thata user has accessed a content item. The access notification may comedirectly from device 100 or from interaction synchronization module 416.The access notification may be generated responsive to detecting apresence event consistent with access of the content item, such asopening a content item for viewing or editing. In one embodiment,notification queue module 428 clears a user notification queue 430responsive to receiving a notification that the associated user viewedthe notification queue. This way, the user will not be presented withnotifications that the user has already viewed.

Content management system 110 may be implemented using a singlecomputer, or a network of computers, including cloud-based computerimplementations. For the purposes of this disclosure, a computer isdevice having one or more processors, memory, storage devices, andnetworking resources. The computers are preferably server classcomputers including one or more high-performance CPUs and 1 G or more ofmain memory, as well as 500 Gb to 2 Tb of computer readable, persistentstorage, and running an operating system such as LINUX or variantsthereof. The operations of content management system 110 as describedherein can be controlled through either hardware or through computerprograms installed in computer storage and executed by the processors ofsuch server to perform the functions described herein. These systemsinclude other hardware elements necessary for the operations describedhere, including network interfaces and protocols, input devices for dataentry, and output devices for display, printing, or other presentationsof data, but which are not described herein. Similarly, conventionalelements, such as firewalls, load balancers, failover servers, networkmanagement tools and so forth are not shown so as not to obscure thefeatures of the system. Finally, the functions and operations of contentmanagement system 110 are sufficiently complex as to requireimplementation on a computer system, and cannot be performed in thehuman mind simply by mental steps.

In one configuration, components described below with reference tocontent management system 110 are incorporated into devices 100 thatshare and synchronize content items without management by contentmanagement system 110. These devices 100 may synchronize content andshare interaction information over network 120 or via a directconnection as described above. In this configuration, devices 100 mayincorporate functionality of synchronization module 412, conflictmanagement module 414, interaction synchronization module 416, and othermodules and data stores for incorporating functionality described belowas provided by content management system 110. Accordingly, devices 100in this configuration operate in a peer-to-peer configuration and may doso without content management system 110 or network 120.

FIG. 5 shows an example process for determining presence informationassociated with a content item according to one embodiment. This processis typically performed by interaction management module 204. Where theuser interface elements are monitored only after being associated with acontent item, interaction management module 204 uses events indicatingthat a content item is being opened by an application or user interfaceelement to determine whether to monitor a user interface element. Thisis one example of an event that may associate a content item with a userinterface element to initiate monitoring of the user interface element,termed a monitoring event. In other embodiments, a selection of userinterface elements to monitor is determined in another way, or all userinterface elements are monitored, in which case the interactionmanagement module 204 may not use monitoring events. In anotherembodiment, the monitoring event includes a process saving a contentitem.

If enabled by operating system 245, the interaction management module204 may register with operating system 245 to receive monitoring eventsfor specific applications. In these embodiments, operating system 245notifies interaction management module 204 when a request to open orsave a content item is received by operating system 245. In thisembodiment, interaction management module 204 receives 500 a monitoringevent that indicates a window or other user interface element isinteracting with a content item, which may be a synchronized contentitem (i.e., the process is interacting with the content item in aparticular user interface element). The monitoring event designates atleast a user interface element that triggered the monitoring event. Inother embodiments, interaction management module 204 monitors eventsassociated with user interface elements from time-to-time (e.g., fiveminute intervals) and queries whether the user interface elements areassociated with any open content items. According to operating system245 and native application 255 configuration, this query may be directedto operating system 245 or native application 255. When a user interfaceelement is associated with a newly opened content item, that newlyopened content item is treated as a monitoring event to determinewhether the newly opened content item is a content item synchronizedwith content management system 110 and that presence information shouldbe determined for the newly opened content item.

When the monitoring event is received, interaction management module 204determines 510 which process is responsible for the user interfaceelement associated with the monitoring event. Interaction managementmodule 204 typically determines the process by requesting the process IDassociated with the user interface element from operating system 245. Insome embodiments, the interaction management module 204 identifies aprocess by requesting an identification of the process from the userinterface element itself.

To confirm that the process and user interface element are correctlyassociated with one another and that the user interface element is stillactive, interaction management module 204 may also request from theprocess the identity of the currently active user interface element. Theinteraction management module 204 confirms that the currently activeuser interface element received from the process matches the userinterface element associated with the monitoring event.

Using the process identifier, interaction management module 204 requests520 any open content item from the process to obtain an associateddirectory path for the content item. The interaction management module204 may designate the user interface element associated with themonitoring event with the request for the open content item's path. Theinteraction management module 204 requests the open item from theprocess or operating system using an interface available interface tothe process or operating system. As one example, in the OS X operatingsystem, the accessibility API may be used to access information relatingto a content item and content item path for a user interface element, asknown in the art. Using the content item path provided by the process,the interaction management module 204 determines whether the openedcontent item path corresponds to any synchronized content items. If so,interaction management module 204 determines that the content itemaccessed by the process is a content item synchronized to contentmanagement system 110 and associates that process and user interfaceelement with the content item. In other embodiments, other methods maybe used to determine whether a content item accessed by the process is asynchronized content item.

If the content item is synchronized 530 to content management system110, interaction management module 204 stores information relating tothe content item, process, and user interface element, to monitor 540the user interface element for events. When the content item associatedwith the monitoring event is not synchronized, the process may end ormay continue by displaying a synchronization interface to a user.Monitoring information is stored in monitored presence data store 210.To monitor and subsequently receive presence events related to the userinterface element, interaction management module 204 registers toreceive events associated with the user interface element. Theregistration process by the interaction management module 204 variesaccording to the configuration of device 100. Typically the interactionmanagement module 204 registers a request to receive presence eventsfrom operating system 245 or from the applicable process or userinterface element. While the monitoring events determine whether a userinterface element or process is associated with a synchronized contentitem, presence events are events that may indicate a change in state ofa user's presence relating to the user interface element or processassociated with a content item. Example presence events include a changein focus of a user interface element, closing a user interface element,closing a content item, opening a content item, and so forth based onthe types of presence recognized by the interaction management module204. In various configurations, the presence events used by interactionmanagement module 204 depend on the events operating system 245 andnative application 255 make available for receipt by interactionmanagement module 204.

The presence events are used to determine presence informationassociated with the content item to which the presence event relates.For example, a presence event indicating that a user interface elementthat is associated with a content item has the focus will indicate thatthe user is viewing the content item, and hence the presence informationfor that content item indicates that state. Likewise, a presence eventindicating that a user interface element unrelated to a content item hasgained focus indicates that the content item associated with apreviously focused user interface element has lost focus, and thusindicates that user is no longer be viewing the content item. Thus,presence information provides a level of semantic interpretation of theunderlying presence event itself.

In addition to receiving presence events that the interaction managementmodule 204 registered for, presence events may also be initiated byinteraction management module 204 to confirm that presence informationhas not changed for a monitored user interface element. These presenceevents may be initiated if a threshold amount of time passed since thelast presence event for a particular user interface element or process,or at particular intervals, e.g., every five minutes.

In addition to registering for presence events, interaction managementmodule 204 may receive interaction events in other ways. In oneembodiment, users may expressly indicate interaction information througha user interface element. The user interface element can be configuredto allow the user to indicate, for example, that a user intends torevise a content item, to indicate that intent to other users who areediting or viewing the content item, for example by selection of a menuitem or icon that represents the particular intent. The user interfaceelement can also be configured to allow a user to indicate otherintentions of the user, such as a user's intention to no longer view acontent item, or to expressly indicate that a user is not or will not bepresent for a content item. Other users may use such “not present”intention to know that the content item is free for editing. User inputinteraction events may also include messages or chat features to bedisseminated to other users associated with the content item, forexample, to transmit a message to other users currently viewing thecontent item on other devices.

When a presence event is received 550, interaction management module 204determines 560 whether any presence information has changed since thelast presence event related to a monitored user interface element. Foruser-initiated interaction information, the interaction information maybe the information provided by the user, for example the user'sselection of a user interface element indicating that the user intendsto modify a content item, or a user's chat message. For presence events,the interaction management module 204 queries the monitored process todetermine the status of the monitored user interface element. Inparticular, the interaction management module 204 queries the process todetermine if the monitored user interface element is the active userinterface element. When the monitored user interface element is theactive user interface element, the content item is being viewed by theuser.

In some embodiments, in addition to detecting user presence with respectto a content item, interaction management module 204 also determineswhether the content item is being or has been modified by the user. Thisfurther aspect enables presence information to be reported moregranularly, for example with an indication that a user has a presencewith respect to the content item as an editor rather than as a viewer.As the particular actions performed by applications when a content itemis being modified may vary as described above, detecting one of theseactions by interaction management module 204 indicates that the processhas edited the content item. For example, according to the type ofactions expected by the process when the content item is edited,interaction management module 204 may query the process to determine ifthe process indicates the content item has been flagged as modified, ifthe title information of the user interface element has changed, if atemporary file has been saved or cached, or any other data that suggeststhe content item has been modified. Interaction management module 204may also query the operating system to determine if a content item hasbeen saved that matches a temporary content item format, for example acontent item with a filename similar to the content item, but with atilde or other specialized variation of the filename. Such modificationsindicate that the presence information associated with the content itemshould reflect that the user is editing the content item.

After determining 560 the presence information, any new presenceinformation for a user interface element may be stored as monitoredpresence data store 250. This presence information in one embodiment isstored on a user interface element-by-user interface element basis, suchthat multiple user interface elements by one process may be associatedwith the same content item, and have presence information individuallymanaged. In one embodiment, presence information may change based on thecurrent presence status. For example, when the presence information fora content item reflects that the content item is being edited, in oneembodiment the presence for the content item in a user interface elementis not changed when a user changes focus to another user interfaceelement. Instead, the edited status is maintained with respect to thatuser interface element until a presence event indicates the userinterface element is closed. In another embodiment, since editing hasthe potential to introduce modifications to the content item, in oneembodiment the presence information for an edited document is notchanged until the interaction management module 204 receives anotification that modifications to the content item are either committedor the modifications are discarded.

A content item with presence information indicating it is being viewedmay have that status change when the user interface element loses focus,or within a threshold period of time of losing focus. This may be thecase even if the user interface element associated with the content itemis still open. In one embodiment, “viewed” presence informationindicates whether a content item is associated with an active userinterface element. In one embodiment, “viewed” presence information isretained until the user interface element is not active (or has lostfocus) for longer than a threshold amount of time. In one embodiment,the content item is considered “viewed” while the content item is openby an application.

When there is a change to the interaction information, interactionmanagement module 204 sends 570 the presence information to contentmanagement system 110. In one embodiment, the sent presence informationincludes an identifier of the content item, the process id, the userinterface element id, and the presence status. The presence informationmay further include metadata, such as versioning notes and presenceevent timestamps.

In one embodiment, the content management system 110 maintains receivedinteraction information for the synchronized content item, for examplein a data store of the content management system 110. The contentmanagement system 110 may provide received interaction information toother devices 100 that are synchronized with respect to the content itemfor display to users.

FIGS. 6A-6D show example user interfaces displaying interactioninformation, including user notification queue content. These userinterfaces may be generated, for example, by user interface module 202,and is one means for doing so. In FIG. 6A, the example window 605 of theuser interface displays a synchronized content item, here “content item6.”. The example user interface displays interaction informationreceived from content management system 110. To display interactioninformation, interaction management module 204 provides interactionindicator(s) 600 along a boundary or border of the window associatedwith the content item.

Interaction indicator 600 is displayed along with the window associatedwith the content item, and in one embodiment interaction managementmodule 204 tracks the location of the window and displays interactionindicator 600 adjacent to or near the window, for example alongside aborder or boundary of the window. The interaction indicator 600 may belocated on any convenient area of display 220. In one embodiment theinteraction indicator is displayed proximal the associated userinterface element of the content item so as to visually indicate to theuser the relationship between the interaction indicator and the specificcontent item. In addition, the display of the interaction indicatoralong a boundary or border of the window increases the likelihood thatthe user will notice interaction indicator 600. In one embodiment, theinteraction indicators 600 are displayed on or alongside a vertical edgeof the window containing the content item (e.g., right edge as shownFIG. 6A). Alternatively, interaction indicator 600 may be shown in aseparate area of the display, such as a taskbar, or tray icon or may bea separate user interface element that does not interact with the userinterface element of the content item. Though shown here as a singleinteraction indicator 600, any number of interaction indicators 600 maybe shown related to the content item.

In FIG. 6B, the interaction indicator 600 includes a badge element 610.Badge element 610 may include a number of other visual elements toprovide more information about interaction information. For example, thebadge element 610 may have a number representing a number of unviewedinteraction events, as illustrated in FIG. 6B. In other embodiments, thebadge element 610 may be a visual element such as an icon to indicateunviewed interaction events to a user.

Turning to FIG. 6C, supplemental interaction indicator 620 may appearwhen a user selects or hovers over interaction indicator 600 to providefurther information or interfaces for the user. In the example shown inFIG. 6C, supplemental interaction indicator 620 describes a recentinteraction with the content item, specifically that Andrew editedcontent item 6. Supplemental interaction indicator 620 may also appearwithout action by the user, for example, when a presence changes, toindicate a new user is viewing or editing the document.

FIG. 6D shows an example user interface with an interaction element 630through which a user may view and enter interaction information. Thisinterface includes interaction indicators 600, in addition to furtheruser interface elements. The interaction element 630 may be presented inlieu of the example of FIGS. 6A-6C, or may be presented as asupplemental element providing additional data regarding the contentitem.

The interaction element 630 includes content item information section646, which displays the content item name, as well as the time of a lastinteraction event, such as a save action. In the example of FIG. 6D, thecontent item information section 646 indicates that Content Item 6 waslast saved 3 minutes ago. The interface also includes sharing element642 that allows users to share the content item with other users, eithervia synchronization or other methods known in the art.

The example interface of FIG. 6D includes interaction viewing section634, which displays interaction information and associated informationto users. Associated information may include times that interactionsoccurred and user information associated with interactions. In theexample of FIG. 6D, interaction viewing section 634 contains messages634A-B and presence information 650A-B. For each item of displayedinteraction information, interaction viewing section 634 containsinteraction times 644A-D. In one embodiment, as shown in FIG. 6D,interaction times 644A-D are expressed as a time that the interactionoccurred. In another embodiment, interaction times may be expressed as arelative time, for example, how much time has elapsed since theinteraction occurred.

The interaction viewing section 634 contains user images 636A-B formessages and other interaction information associated with users. Userimages 636A-B may be received from the content management system 110.The interaction viewing section 634 contains user identifiers 648A-B,which may be user IDs, names, or other identifiers. The interactionviewing section 634 may include other icons or graphics for interactioninformation. For example, icons 638A-B may correspond to displayedpresence information. Icon 638A is an eye to represent viewing, and icon638B is a pencil to represent editing or saving a new version.

In one embodiment, users may interact with (e.g., click, hover over,etc.) various elements within the interaction viewing section 634 toview additional information. For example, selecting or hovering overname elements 648A-B or user images 636A-B may allow the user to viewadditional user information related to that user.

This interface also provides a chat interface for users to communicatewith other users associated with the content item. The chat interfacepermits users to enter and receive messages to other users. A text inputelement 632 allows users to enter messages to other users, andinteraction viewing element 634 allows users to view messages. The chatinterface may permit users to specifically discuss information relatingto that content item, such as when a user expects to finish editing theitem. These messages are received by interaction management module 204as interaction information and sent to other clients synchronized to thecontent item. This permits users to chat directly about a content item,even if the native application provides no chat functionality.

FIG. 7 shows an example process for updating notification queues forsharing users according to one embodiment. Content management system 110receives 702 a notification of an interaction event for a shared contentitem. The interaction event indicates a new interaction with the sharedcontent item by a sharing user, which we refer to here for purposes ofexplanation as “User A.”

In one embodiment, content management system 110 determines 704 whetherusers are collaborating in the content item—that is, whether more thanone user currently has the document open for viewing or editing. Ifusers are collaborating in the content item, the process ends, and thenotification is not added to the users' notification queues. If usersare not currently collaborating in the content item, the contentmanagement system 110 proceeds with updating the notification queues forthe content item for each sharing user.

Content management system 110 determines 706 the interaction type andthe priority of the new interaction. Content management system 110 usesthe interaction type and the priority of the new interaction todetermine whether to add the interaction to each user's notificationqueue for the content item. For each sharing user, content managementsystem 110 determines 710 whether the notification queue alreadyincludes an interaction by the sharing user A with a higher prioritythan the priority of the new interaction. If the notification queue doesalready include a higher priority interaction by the sharing user A, thenotification queue is not updated, and the process proceeds from step708 with the next user. If the notification queue does not alreadyinclude a higher priority interaction by the sharing user A, contentmanagement system 110 adds 712 the new interaction to the notificationqueue. In one embodiment, content management system 110 removes 714lower priority interactions by the sharing user A from the notificationqueue.

FIG. 8 shows an example process for sending a notification queue to adevice accessing a content item according to one embodiment. Contentmanagement system 110 receives 802 a notification that a content item isaccessed by sharing user B. Content management system 110 determines 804whether the sharing user B is collaborating in the content item. If thesharing user B is collaborating in the content item, content managementsystem 110 clears 806 the sharing user B's notification queue for thecontent item without delivering the queue. Alternatively, if the sharinguser B is not collaborating in the content item, content managementsystem 110 sends the sharing user B's notification queue for the contentitem to a device 100 of the sharing user B.

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a non-transitory, tangible computer readable storagemedium, or any type of media suitable for storing electronicinstructions, which may be coupled to a computer system bus.Furthermore, any computing systems referred to in the specification mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

Embodiments of the invention may also relate to a product that isproduced by a computing process described herein. Such a product maycomprise information resulting from a computing process, where theinformation is stored on a non-transitory, tangible computer readablestorage medium and may include any embodiment of a computer programproduct or other data combination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

What is claimed is:
 1. A method comprising: receiving a notification ofan interaction event indicating an interaction with a content item by afirst user of a plurality of users, the content item synchronizedbetween a content management system and a plurality of devices, eachdevice associated with one of the plurality of users with which thecontent item is shared; and for a second user of the plurality of users:adding the interaction to a notification queue corresponding to thesecond user; receiving, from a presence application on a deviceassociated with the second user, an indication that the content item hasbeen opened in a native application of the device, the presenceapplication monitoring interactions with content items by the nativeapplication; and in response to the indication that the content item hasbeen opened, sending the notification queue corresponding to the seconduser to the presence application.
 2. The method of claim 1, wherein thepresence application is configured to display the notification queuewithin a first interface element of the presence application.
 3. Themethod of claim 2, wherein the native application is configured todisplay the content item within a second interface element of the nativeapplication, and wherein the second interface element is independent ofthe first interface element.
 4. The method of claim 1, wherein thepresence application is associated with a first operating system processof the device and the native application is associated with a secondoperating system process of the device.
 5. The method of claim 1,wherein the presence application is not integrated into the nativeapplication.
 6. The method of claim 1, wherein the presence applicationis configured to monitor interactions with content items by a pluralityof different native applications.
 7. The method of claim 1, wherein theinteraction is added to the notification queue at a location within thenotification queue based on a priority of the interaction relative to apriority of notifications within the notification queue.
 8. The methodof claim 1, wherein the interaction event indicates that the first userviewed the content item.
 9. The method of claim 1, wherein theinteraction event indicates that the first user edited the content item.10. The method of claim 1, wherein the interaction event indicates thatthe first user made a comment on the content item.
 11. The method ofclaim 1, wherein the interaction event indicates that the first userrequested a collaboration on the content item with the second user. 12.The method of claim 1, wherein the interaction event includes anindication by the first user that the first user intends to edit thecontent item.
 13. The method of claim 1, wherein the interaction eventindicates that the first user has modified metadata corresponding to thecontent item.
 14. The method of claim 1, wherein the interaction eventindicates a request for versioning information corresponding to thecontent item.
 15. A system comprising: a processor configured to executeinstructions; and a non-transitory, computer-readable storage mediumstoring instructions, which when executed by the processor cause theprocessor to perform steps comprising: receiving a notification of aninteraction event indicating an interaction with a content item by afirst user of a plurality of users, the content item synchronizedbetween a content management system and a plurality of devices, eachdevice associated with one of the plurality of users with which thecontent item is shared; and for a second user of the plurality of users:adding the interaction to a notification queue corresponding to thesecond user; receiving, from a presence application on a deviceassociated with the second user, an indication that the content item hasbeen opened in a native application of the device, the presenceapplication monitoring interactions with content items by the nativeapplication; and in response to the indication that the content item hasbeen opened, sending the notification queue corresponding to the seconduser to the presence application.
 16. The system of claim 15, whereinthe presence application is configured to display the notification queuewithin a first interface element of the presence application.
 17. Thesystem of claim 16, wherein the native application is configured todisplay the content item within a second interface element of the nativeapplication, and wherein the second interface element is independent ofthe first interface element.
 18. The system of claim 15, wherein thepresence application is associated with a first operating system processof the device and the native application is associated with a secondoperating system process of the device.
 19. The system of claim 15,wherein the presence application is not integrated into the nativeapplication.
 20. A non-transitory computer-readable storage mediumstoring executable instructions that, when executed by a processor,cause the processor to perform steps comprising: receiving anotification of an interaction event indicating an interaction with acontent item by a first user of a plurality of users, the content itemsynchronized between a content management system and a plurality ofdevices, each device associated with one of the plurality of users withwhich the content item is shared; and for a second user of the pluralityof users: adding the interaction to a notification queue correspondingto the second user; receiving, from a presence application on a deviceassociated with the second user, an indication that the content item hasbeen opened in a native application of the device, the presenceapplication monitoring interactions with content items by the nativeapplication; and in response to the indication that the content item hasbeen opened, sending the notification queue corresponding to the seconduser to the presence application.